fix(compliance): register the published and qualified 3.2.11 hosted bundle - #8985

) and enforced_policies gate for policy_backed_rejections (#8850) (#8938)

* fix(compliance): sign functional dispatch with a key no vector uses (#8889)

test-kits
- sign functional dispatch with dedicated test-functional-2026 key
- scope the lowered rate_abuse grading cap to the vector 020 keyid

test-vectors
- publish test-functional-2026 in request-signing keys.json
- document revoked and functional keys in the README key table

docs
- list test-functional-2026 among untrusted test kids
- name the functional key in signed-requests prerequisites

tests
- assert no conformance vector signs with the functional keyid
- assert the published functional key pair is consistent

(cherry picked from commit e9c2162)

Backport of #8889 to 3.2.x (fixes #8877). Clean cherry-pick; no 3.2.x adaptation was needed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(compliance): gate policy_backed_rejections on published enforced_policies (3.2.x)

creative/policy_backed_rejections seeds a product with enforced_policies
through the controller and then asserted that the seller published and
enforced both fixture policies. A seller that never claimed registry
policy enforcement failed it, and the 3.2 schemas give it no capability to
opt out (adcp#8850). Main gates the storyboard on the new 3.3
creative.supports_registry_policy_enforcement capability (adcp#8857); a
new capability field is not patch-eligible here.

This line gates on what the seller publishes instead. The discovery read
asserts only a schema-valid get_products response and captures the
returned products. The policy-universe confirmation and the dual-violation
sync_creatives phases carry
  skip_if: "!context.policy_products.0.enforced_policies.0"
so they run only when the first discovered product carries a non-empty
enforced_policies list. The gate reads the seller's response, not the
seed. A seller that omits the field, publishes an empty list, or returns
no products is not sent the violating creative and is not failed. A
seller that publishes any enforced policy runs every step and is still
graded on the exact two-policy universe and one CREATIVE_REJECTED entry
per policy.

Regression tests run the storyboard on both the maintenance runner
(@adcp/sdk 14.0.0-rc.53) and the private modern runner (17.0.0-beta.3).

Refs #8850

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Synaeve <synaeve@idmgroup.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

…rt) (#8864)

* fix(schemas): open the 3.2 schemas that were meant to be open

The WG decided on 2026-11-09 that 3.x opens the schemas that were meant
to be open, so a 3.2 validator does not reject a newer 3.x payload just
because a schema was closed. This is the 3.2.10 backport of the 3.3
opening. additionalProperties goes from false to true at 671 of the 775
closed locations in the 3.2 source tree.

104 locations stay closed, by the keep-closed list approved for 3.3;
every file/pointer the two lines share has the same class: oneOf
branches told apart only by key presence, the signed commercial terms
and the must-understand proposal budget constraint, metric qualifiers
and forecast dimensions (join keys), the JWS response envelope, privacy
boundaries (TMP match requests, the not-found error, permission-denied
and billing-not-permitted details, get_principal and sync_principal
results, the get_reporting_status unavailable lookup), the
credential-free reporting destinations and their setup action,
placement-presentation (no key material or markup), and
patternProperties maps keyed by IDs.

The get_reporting_status unavailable-lookup branch stays closed on 3.2.x
with the envelope redeclared; 3.3 opens it under #8547's envelope rule
and enforces the same clamp with named rejections.

The MCP model-context projection drops boolean additionalProperties,
true as well as false (ported from f5c56db on main), so the opening
does not inflate the prompt view. Tests that pinned closure now assert
the opened behavior or compare against the source schema.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(schemas): name the fields closure used to reject in opened 3.2 schemas

Ports #8866's named rejections to 3.2.x for every node that exists
there: where closure was the only thing rejecting a specific field the
protocol defines elsewhere or forbids, the opened schema rejects it by
name in `not`, next to additionalProperties: true. 31 of #8866's 51
named rejections apply on 3.2.x; the rest target schemas or nodes that
3.2.x does not have.

Also ports #8866's description cleanups: opened schemas no longer say
they are closed, and the metric-qualifier descriptions say new keys
ship in a major release. The 3.3-only boolean-demographics deprecation
and gender-targeting wording are not ported.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test: expect opened 3.2 schemas to accept unknown keys

Ports #8866's test edits for the test files 3.2.x has: generic
unknown-key assertions now expect the key to validate, citing DR-0009
(DR-0036 is not on 3.2.x), and the training agent test shows an unknown
hard overlay requirement still matches no product.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(schemas): keep key-presence anyOf unions apart by name on 3.2.x

Ports #8866's 9bda16d and 32768d4 to 3.2.x. Opening exposed
anyOf unions whose branches were told apart only by which keys are
present; each branch now rejects its sibling's keys by name: geo-region
requirement and support countries (all_values vs values), the canonical
account ref (account_id vs brand + operator), the deprecated
fused-system postal area (no country), and sync_reporting_receipts
results (receipt vs adjustment_receipt). Also names `step` on frequency
cap impression constraints and `mode` on list-application receipts.

Tests: adds canonical-account-ref.test.cjs (loading source schemas, as
3.2.x tests do), strips the format-key prohibitions from the MCP
legacy-graph check, and flips the generic unknown-key vectors, citing
DR-0009. PARITY_COMPILE_LIMIT is unchanged on 3.2.x; it does not trip.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(training-agent): omit default openness from bundled tools/list definitions on 3.2.x

Ports the tools/list and parity-test parts of 9c1c52d (#8866):
bundled definitions in the product-discovery tools/list schemas omit
`additionalProperties: true`, which is JSON Schema's default and carries
no information. The root keeps the keyword. The parity test compares
openness rather than the literal keyword.

The sync_principal part of 9c1c52d does not apply: the 3.2 training
agent does not implement sync_principal.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(schemas): mirror #8866's review fixes on 3.2.x

Ports cd8bc76 (Konstantin Mirin's review of #8866) for every node
3.2.x shares:

- Key-presence guards: account-ref's account_id and natural-key forms
  exclude each other, as canonical-account-ref's now do for all six
  natural-key fields; image bleed is uniform or per-side; a failed
  reporting-receipt result carries no receipt.
- Named rejections only for names the protocol defines elsewhere or
  forbids: step, gpc_honored, political, threshold_rate and
  per_ad_spend are dropped, and list-application receipts reject
  auth_token alone. access_token on the delivery-ready webhook stays as
  a credential clamp.
- Each node or union with a named rejection says in its description
  what it rejects and why. The sync_creatives sentence omits the merge
  op 3.2.x does not have, and the closed lookup_unavailable branch
  states its clamp in 3.2.x terms.
- The get_principal current branch and the sync_principal applied and
  validated branches open; the validated branch rejects destination_ref
  and configuration_version.

The changeset calls the commercial terms a hold until 4.0 rather than
a structural reason. 674 of 775 locations open; 101 stay closed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test: flip probes for dropped rejections; add account-ref and bleed guards

Ports c01b095 (#8866) for the test files 3.2.x has: probes for the
dropped rejections expect acceptance (DR-0009); account-ref.test.cjs
and image-bleed.test.cjs are new (loading source schemas, as 3.2.x
tests do) and wired into test:schemas; canonical-account-ref covers
the extended guard. The MCP legacy-graph check walks the parsed schema
and skips `not` and descriptions, and the model-context projection
omits named rejections beside declared properties, as it omits bounds.
PARITY_COMPILE_LIMIT is unchanged on 3.2.x; it does not trip.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: describe refine scope branches and policy entries as open on 3.2.x

The refine[] scope branches and governance policy entries are open on
3.2.x now. A pre-rename refine entry still fails validation, because its
generic `id` doesn't supply the `product_id` or `proposal_id` its scope
requires; the troubleshooting section shows the error the opened schema
gives. A policy-entry field outside the table has no defined meaning, so
receivers ignore it; partner metadata still belongs under `ext`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: give the real reasons for the sync_plans and account-ref statements

The sync_plans plan item is open on 3.2.x, so the governance agent's
bookkeeping fields are simply not declared there, rather than excluded
by closure. The two AccountRef variants are told apart by named
rejections: the account_id variant rejects the natural-key fields and
the natural-key variant rejects account_id, so {account_id, brand}
still fails both.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: match #8866's wording for the opened-schema statements

Aligns the refine troubleshooting, policy-entry, sync_plans and
AccountRef passages with #8866 (6c689cc), including the two
calling-an-agent error-table rows that named additionalProperties.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(schemas): reserve the plan_hash bookkeeping names on sync_plans plans

Ports fa7aefa (#8866). The opened sync_plans plan item accepted the
governance agent's bookkeeping names: version, status, syncedAt,
revisionHistory, committedBudget and committedByType. The plan_hash
profile strips exactly those names from its preimage, so a buyer value
under one of them would sit outside the hash and could collide with
state the agent manages. The plan item now rejects them by name, and its
description says they are reserved and a buyer MUST NOT send them. The
list matches 3.2's closed "Excluded fields" list. No storyboard, fixture
or request example sends them. The test loads source schemas, as 3.2.x
tests do, and cites DR-0009.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(refinement): match the troubleshooting heading to the error it shows

Ports 7d4dd1b (#8866): the heading names the error the opened refine
branches give, and the text says which identifier each scope requires.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

…ush (#8397) (#8959)

* fix(release): tolerate pulls API lag after the fence's acknowledged push

Two of four release runs on main quarantined the 3.3.0-beta.0 Version
Packages transaction (#7897) because the PR read ~0.6s after an acknowledged
push still showed the prior head; the API reported the pushed head seconds
later. The post-push check now polls (10 x 1s) only while the same PR, still
Draft, reports the prior head. Any other mismatch, or a longer lag, fails and
quarantines exactly as before.



* fix(release): record fence PR-head lag as a state event; test Ready during lag



* test(release): lagging pulls stub reads without a check-then-use race



---------


(cherry picked from commit 8f4ab4a)

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Publishing @adcp/sdk 16.7.1 (latest / adcp-3.2, 2026-11-12 18:07Z)
shipped the 3.1.33 compliance bundle, so the 3.2.x publication-manifest
check has failed Build Check since then, including the 3.2.11 backports.

Integrate only the published 3.1.33 records, following #8825 (3.1.32):
the immutable compliance bundle, schemas and signed protocol tarball,
taken unchanged from v3.1.33 (tree hashes match main), the manifest
registration, regenerated root schema discovery, and the release notes.
The 3.1 hosted alias floor advances to 3.1.33 and 3.1.32 stays pinned as
an explicit target.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Version Packages

Forward-merges the published 3.2.11 release (3.2.x = v3.2.11 =
9df1dd7, the #8942 Version Packages merge) and the 3.2.x commits since
v3.2.10: #8873, #8938, #8864, #8959 and #8961.

Release records:
- dist/compliance/3.2.11, dist/schemas/3.2.11 and the signed
  dist/protocol/3.2.11.tgz tuple are taken from v3.2.11 unchanged.
- dist/schemas/index.json and latest.json are regenerated
  (forward-merge-release-records.cjs schema-discovery).
- CHANGELOG.md is main's file plus the 3.2.11 block
  (forward-merge-release-records.cjs changelog).
- package.json, package-lock.json, static/schemas/source/index.json: main's.
- static/compliance/published-versions.json: main's. 3.2.x's only extra
  entry is 3.2.11, which is registered in a separate commit after
  qualification.

#8961's 3.1.33 records already equal main's (same tree hashes). #8959 and
the #8889 half of #8938 are cherry-picks of main commits and auto-merged
to main's bytes.

Content conflicts, all resolved to main's file. Each 3.2.x side is a 3.2
backport or 3.2-only adaptation of work main carries in its 3.3 form:
- 33 schema sources under static/schemas/source and 14 test files, from
  #8864 (the 3.2 backport of main's schema opening and #8866's named
  rejections). Main's copies are the 3.3 opening: no location 3.2.11
  opens is closed on main, and the tests cite DR-0036.
- tests/policy-backed-rejections-storyboard.test.cjs, from the #8850 half
  of #8938: main tests its capability-gated storyboard (#8857).
- docs/media-buy/media-buys/lifecycle.mdx, from #8873: the 3.2
  pending_creatives prose. Main's prose matches main's 3.3 enum.
- server/tests/unit/storyboards.test.ts, from #8961: 3.2.x's floors and
  pins. Main keeps its own.

Auto-merge reverted: the non-conflicting #8850 hunk in
creative/policy_backed_rejections.yaml. It adds the 3.2-only
enforced_policies skip_if gate on top of main's
creative.supports_registry_policy_enforcement capability gate, and its
own narrative says the 3.3 line uses the capability instead.

Outside dist/ and CHANGELOG.md the merged tree equals main's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…undle

Adds 3.2.11 to static/compliance/published-versions.json with
registerPublishedVersion, so the hosted 3.2 alias resolves to 3.2.11.
Exact pins are unchanged. Raises the hosted 3.2 alias floor in
storyboards.test.ts to 3.2.11, as the 3.2.8, 3.2.9 and 3.2.10
registrations did, so the manifest cannot silently lose the release.

Qualification: v3.2.11 is a published GitHub Release with exactly four
assets; the .sha256 verifies; the CDN tarball tuple is byte-identical to
the release assets and to dist/protocol; CDN compliance/3.2.11/index.json
reports published_version 3.2.11 and equals the committed index. The
compiled-server runtime smoke passes for all 69 published versions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>